Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

0496

reference: 142-tree-1
name: 0496
tree-preservation-order: undefined
142-tpo-1
uprn
address-text
point: POINT (-1.002954 50.852578)
geometry: MULTIPOLYGON (((-1.002826 50.852564,-1.002832 50.852590,-1.002850 50.852612,-1.002878 50.852630,-1.002913 50.852642,-1.002952 50.852646,-1.002992 50.852643,-1.003028 50.852632,-1.003057 50.852614,-1.003075 50.852592,-1.003082 50.852567,-1.003076 50.852542,-1.003059 50.852519,-1.003031 50.852501,-1.002995 50.852489,-1.002956 50.852485,-1.002916 50.852488,-1.002880 50.852499,-1.002852 50.852517,-1.002833 50.852540,-1.002826 50.852564)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL